Components of a Default Cluster |
|
Syncup instances are of three types: master, local, or remote. These are described in the table below.
Note: A SyncUp instance type is determined based on the protocol used by it.
Master Syncup |
Local Syncup |
Remote Syncup |
|---|---|---|
OpenText Process Suite Platform (<instance name>)s constitute the members of the cluster. |
Each instance of local SyncUp is associated with an instance of master SyncUp on that machine. |
An instance of remote SyncUp is arbitrarily associated with the instance of master SyncUp, on a different machine. |
The messages between these instances are communicated over TCP. |
Communication between the master SyncUp and local SyncUp is one-to-one, and is through TCP. |
Communication between the master SyncUp and remote SyncUp is one-to-one and is through the TCP protocol. |
Each instance in the cluster has a unique identifier. |
The unique identifier of master SyncUp is used by the local SyncUp. |
- |
Instances can either use state registry or broadcast communication types, to communicate with each other. |
Instances can either use state registry or broadcast communication types to communicate with each other. |
A remote SyncUp instance can use only the stateless transfer of data mechanism to send messages across the cluster. |
Each instance can either insert, update or delete only a designated part of the state registry (shared data in XML). |
Each instance can either insert, update or delete only a designated part of the state registry (shared data in XML). |
Remote SyncUp can read the information within the state registry but cannot modify its contents. |
Each instance of the master SyncUp can subscribe to any topic or publish message on any topic. |
Each instance can subscribe to any topic or publish message on any topic. |
Each instance can subscribe to any topic or publish message on any topic. |